AI Prompt Library

Business Case Template
1  Start a chat in ChatGPT, Claude, or Gemini and attach two files from your kit folder: Business Case Template 16x9.pptx and Business Case Template Map.txt 2  Copy any prompt below, paste it into the chat, and answer its questions
Built for the SlideStart Business Case Template · 16:9 build, 320 slides (June 2026) · 320 slides mapped with measured word limits · in tools that can run code, deck prompts return the assembled .pptx
Send feedbackopens your mail app — or email team@slidestart.com
Slide 1 of the Business Case Template

One prompt runs the entire build: it interviews you, reads anything you attach, plans the deck from this template's layouts, then writes every slide — and in ChatGPT or Claude, hands back the assembled .pptx.

Full business case
The complete case: problem, options, recommendation, financials, plan, ask.
14–18 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a full business case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you proposing, in one sentence, and who has to approve it?
2. The problem or opportunity — what happens if nothing is done? Numbers if you have them.
3. The options you considered (I'll include "do nothing" unless you say otherwise)?
4. Your recommended option, and the two or three reasons it wins?
5. Costs and benefits: investment required, expected returns, payback? Attach any model outputs.
6. The implementation plan: phases, timeline, who delivers?
7. The main risks, honestly, and mitigations?
8. Exactly what decision or approval do you need, by when?
Finish with three build questions: how many slides (suggest 14–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the ask up front -> the problem (price the status quo — the iceberg earns its place) -> options considered (pros/cons tables) -> the recommendation -> costs and benefits -> implementation plan -> risks -> the decision needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a full business case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you proposing, in one sentence, and who has to approve it?
2. The problem or opportunity — what happens if nothing is done? Numbers if you have them.
3. The options you considered (I'll include "do nothing" unless you say otherwise)?
4. Your recommended option, and the two or three reasons it wins?
5. Costs and benefits: investment required, expected returns, payback? Attach any model outputs.
6. The implementation plan: phases, timeline, who delivers?
7. The main risks, honestly, and mitigations?
8. Exactly what decision or approval do you need, by when?
Finish with three build questions: how many slides (suggest 14–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the ask up front -> the problem (price the status quo — the iceberg earns its place) -> options considered (pros/cons tables) -> the recommendation -> costs and benefits -> implementation plan -> risks -> the decision needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Capital investment approval
A capex case: the asset, the economics, the alternatives, the approval.
12–16 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a capital investment approval using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the investment and how much?
2. What does it buy — capacity, capability, compliance, replacement?
3. The economics: NPV, IRR, payback, or whatever your process uses? Attach the model.
4. Alternatives considered, including deferral?
5. What happens to operations if this isn't approved?
6. Delivery: who, when, key dependencies?
7. Which approval gate is this, and what does the committee care about?
Finish with three build questions: how many slides (suggest 12–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the ask and headline economics -> the need -> alternatives (including deferral) -> the recommended investment -> financial detail (chart-heavy) -> delivery plan -> risks -> approval requested. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a capital investment approval using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the investment and how much?
2. What does it buy — capacity, capability, compliance, replacement?
3. The economics: NPV, IRR, payback, or whatever your process uses? Attach the model.
4. Alternatives considered, including deferral?
5. What happens to operations if this isn't approved?
6. Delivery: who, when, key dependencies?
7. Which approval gate is this, and what does the committee care about?
Finish with three build questions: how many slides (suggest 12–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the ask and headline economics -> the need -> alternatives (including deferral) -> the recommended investment -> financial detail (chart-heavy) -> delivery plan -> risks -> approval requested. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Options analysis & recommendation
A fair fight between real alternatives, ending in a recommendation.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a options analysis & recommendation using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What decision is being made, and who makes it?
2. The options — all of them, including the ones you don't like?
3. The criteria the audience actually decides on (cost, risk, speed, fit)?
4. Your scoring or evidence per option? Attach anything you have.
5. Your recommendation, and the runner-up's strongest point?
6. What would change your mind?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the decision at stake -> the options introduced fairly -> criteria -> the comparison (pros/cons tables 206/207, checkmarks 198/199, or weighing scales) -> scoring summary -> recommendation that concedes the runner-up's strongest point -> next steps. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a options analysis & recommendation using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What decision is being made, and who makes it?
2. The options — all of them, including the ones you don't like?
3. The criteria the audience actually decides on (cost, risk, speed, fit)?
4. Your scoring or evidence per option? Attach anything you have.
5. Your recommendation, and the runner-up's strongest point?
6. What would change your mind?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the decision at stake -> the options introduced fairly -> criteria -> the comparison (pros/cons tables 206/207, checkmarks 198/199, or weighing scales) -> scoring summary -> recommendation that concedes the runner-up's strongest point -> next steps. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Cost-benefit / ROI case
The economics of one move: costs, benefits, sensitivity, verdict.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a cost-benefit / roi case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the move being evaluated?
2. All the costs — one-time and recurring, including the ones people forget?
3. The benefits — hard savings, revenue, avoided costs, soft benefits kept separate?
4. Time horizon and any discounting convention your finance team uses?
5. The base case numbers? Attach the model or spreadsheet.
6. What drives the result — the 2-3 assumptions that matter most?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the verdict up front (stat callouts) -> costs in full -> benefits, hard and soft kept honest -> the net picture over time (charts) -> sensitivity: what breaks it -> recommendation and conditions. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a cost-benefit / roi case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What's the move being evaluated?
2. All the costs — one-time and recurring, including the ones people forget?
3. The benefits — hard savings, revenue, avoided costs, soft benefits kept separate?
4. Time horizon and any discounting convention your finance team uses?
5. The base case numbers? Attach the model or spreadsheet.
6. What drives the result — the 2-3 assumptions that matter most?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the verdict up front (stat callouts) -> costs in full -> benefits, hard and soft kept honest -> the net picture over time (charts) -> sensitivity: what breaks it -> recommendation and conditions. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Vendor or solution selection
Requirements, shortlist, scoring, and the pick.
12–16 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a vendor or solution selection using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you buying, and what process got you to this shortlist?
2. The requirements that matter, weighted if you weight them?
3. The vendors or solutions on the shortlist?
4. Scores or findings per vendor — demos, references, pricing? Attach the scoring sheet.
5. Commercial comparison: pricing structures, contract terms?
6. Your recommendation and the implementation implications?
Finish with three build questions: how many slides (suggest 12–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: what we're buying and why -> requirements -> the shortlist -> the comparison (checkmark tables 198/199, comparison tables 210-213, pricing 100-103) -> references and risks -> the pick -> contract and next steps. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a vendor or solution selection using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you buying, and what process got you to this shortlist?
2. The requirements that matter, weighted if you weight them?
3. The vendors or solutions on the shortlist?
4. Scores or findings per vendor — demos, references, pricing? Attach the scoring sheet.
5. Commercial comparison: pricing structures, contract terms?
6. Your recommendation and the implementation implications?
Finish with three build questions: how many slides (suggest 12–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: what we're buying and why -> requirements -> the shortlist -> the comparison (checkmark tables 198/199, comparison tables 210-213, pricing 100-103) -> references and risks -> the pick -> contract and next steps. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Pilot results & scale-up case
What the pilot proved, and the case for rolling it out.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a pilot results & scale-up case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What was piloted, where, and for how long?
2. What the pilot was designed to prove?
3. The results — the numbers, honestly, including what didn't work? Attach the data.
4. What changes between pilot and scale (cost per unit, complexity, support)?
5. The scale-up plan and investment?
6. What decision do you need to proceed?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: what we set out to prove -> the pilot design (credibility) -> results (chart-heavy, including the misses) -> what scale changes -> the rollout plan -> economics at scale -> the decision needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a pilot results & scale-up case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What was piloted, where, and for how long?
2. What the pilot was designed to prove?
3. The results — the numbers, honestly, including what didn't work? Attach the data.
4. What changes between pilot and scale (cost per unit, complexity, support)?
5. The scale-up plan and investment?
6. What decision do you need to proceed?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: what we set out to prove -> the pilot design (credibility) -> results (chart-heavy, including the misses) -> what scale changes -> the rollout plan -> economics at scale -> the decision needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Budget or headcount request
What you need, what it delivers, and what happens without it.
8–12 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a budget or headcount request using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you asking for — money, people, or both — and how much?
2. What it funds, concretely?
3. What it delivers — tied to which targets or commitments?
4. What happens if it's not approved, specifically?
5. Options you can offer: the full ask vs. a reduced version and what each buys?
6. Who approves, and what do they push back on historically?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the ask on slide one -> what it funds -> what it delivers (tie every dollar to an outcome) -> the cost of not funding -> tiered options if useful (pricing layouts work well) -> the decision needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a budget or headcount request using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What are you asking for — money, people, or both — and how much?
2. What it funds, concretely?
3. What it delivers — tied to which targets or commitments?
4. What happens if it's not approved, specifically?
5. Options you can offer: the full ask vs. a reduced version and what each buys?
6. Who approves, and what do they push back on historically?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the ask on slide one -> what it funds -> what it delivers (tie every dollar to an outcome) -> the cost of not funding -> tiered options if useful (pricing layouts work well) -> the decision needed. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Project approval (charter)
Scope, plan, resourcing, governance — the project's founding document.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a project approval (charter) using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. The project in one sentence, and the problem it solves?
2. Scope — and what's explicitly out of scope?
3. The plan: phases, milestones, key dates?
4. Resourcing: team, budget, external help?
5. Governance: sponsor, steering, decision rights?
6. Success criteria — how will anyone know it worked?
7. The risks you already see?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: why this project, why now -> scope in/out -> the plan (roadmaps 124-126 or timelines) -> resourcing -> governance (org and responsibility layouts) -> success criteria -> risks -> approval requested. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a project approval (charter) using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. The project in one sentence, and the problem it solves?
2. Scope — and what's explicitly out of scope?
3. The plan: phases, milestones, key dates?
4. Resourcing: team, budget, external help?
5. Governance: sponsor, steering, decision rights?
6. Success criteria — how will anyone know it worked?
7. The risks you already see?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: why this project, why now -> scope in/out -> the plan (roadmaps 124-126 or timelines) -> resourcing -> governance (org and responsibility layouts) -> success criteria -> risks -> approval requested. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Steering committee decision paper
Status, the issue on the table, options, and the decision needed today.
8–12 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a steering committee decision paper using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What program, what period, and who sits on the steering committee?
2. Status vs. plan — the honest numbers?
3. The issue or decision on the table today?
4. The options for that decision, with your recommendation?
5. What each option means for timeline, cost, and risk?
6. What exactly do you need the committee to say yes to?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: status at a glance -> what changed since last time -> the issue on the table -> options (pros/cons) -> the recommendation and its implications -> the decision needed today, verbatim. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a steering committee decision paper using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What program, what period, and who sits on the steering committee?
2. Status vs. plan — the honest numbers?
3. The issue or decision on the table today?
4. The options for that decision, with your recommendation?
5. What each option means for timeline, cost, and risk?
6. What exactly do you need the committee to say yes to?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: status at a glance -> what changed since last time -> the issue on the table -> options (pros/cons) -> the recommendation and its implications -> the decision needed today, verbatim. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Cost reduction / efficiency case
Where the money is, how to get it, and what it takes.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a cost reduction / efficiency case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What area or cost base, and how big is it today?
2. Where the savings opportunities are — with sizes if you have them? Attach any analysis.
3. How each saving is captured: quick wins vs. structural moves?
4. One-time costs to achieve the savings?
5. What could go wrong — service levels, morale, capacity?
6. The ask: mandate, investment, or both?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the cost base today -> the opportunity (stat callouts, charts) -> the levers, quick wins first -> cost to achieve -> net savings over time -> risks and safeguards -> the mandate requested. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a cost reduction / efficiency case using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What area or cost base, and how big is it today?
2. Where the savings opportunities are — with sizes if you have them? Attach any analysis.
3. How each saving is captured: quick wins vs. structural moves?
4. One-time costs to achieve the savings?
5. What could go wrong — service levels, morale, capacity?
6. The ask: mandate, investment, or both?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the cost base today -> the opportunity (stat callouts, charts) -> the levers, quick wins first -> cost to achieve -> net savings over time -> risks and safeguards -> the mandate requested. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Turn my data or document into a deck
Attach a spreadsheet, model, or notes — get a business case built around them.
10–16 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a turn my data or document into a deck using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Attach or paste your material first (spreadsheet, model outputs, notes — anything).
2. What decision is this deck asking for, and from whom?
3. What's the single takeaway someone should leave with?
4. Anything the material doesn't say that you know matters?
Finish with three build questions: how many slides (suggest 10–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: let the material drive. Lead each section with the chart, stat, or table layout that fits the data's actual shape, and use text layouts (12-14) to say what each number means. State the ask on slide one. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a turn my data or document into a deck using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. Attach or paste your material first (spreadsheet, model outputs, notes — anything).
2. What decision is this deck asking for, and from whom?
3. What's the single takeaway someone should leave with?
4. Anything the material doesn't say that you know matters?
Finish with three build questions: how many slides (suggest 10–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: let the material drive. Lead each section with the chart, stat, or table layout that fits the data's actual shape, and use text layouts (12-14) to say what each number means. State the ask on slide one. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Build vs. buy decision
The classic make-or-buy: capabilities, costs, risks, verdict.
10–14 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a build vs. buy decision using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What capability or system is being decided?
2. The build option: what it takes, how long, who does it?
3. The buy option(s): vendors, pricing, fit gaps?
4. Total cost of each over a sensible horizon? Attach any modeling.
5. Strategic considerations: differentiation, lock-in, talent?
6. Your leaning, and what would flip it?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the capability at stake -> option A: build -> option B: buy -> head-to-head (versus list 205, pros/cons 206, weighing scale) -> total cost comparison (charts) -> strategic factors -> verdict and conditions. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Click to copy prompt
Build me a build vs. buy decision using my SlideStart Business Case Template.

I've attached "Business Case Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What capability or system is being decided?
2. The build option: what it takes, how long, who does it?
3. The buy option(s): vendors, pricing, fit gaps?
4. Total cost of each over a sensible horizon? Attach any modeling.
5. Strategic considerations: differentiation, lock-in, talent?
6. Your leaning, and what would flip it?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the capability at stake -> option A: build -> option B: buy -> head-to-head (versus list 205, pros/cons 206, weighing scale) -> total cost comparison (charts) -> strategic factors -> verdict and conditions. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight list. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.

AI Prompt Library · 16:9 build, 320 slides (June 2026) · Works with ChatGPT, Claude, and Gemini.  ·  Send feedback (team@slidestart.com)